Set the IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaallll SSSSttttaaaannnnddddaaaarrrrdddd RRRReeeeccccoooorrrrddddiiiinnnngggg NNNNuuuummmmbbbbeeeerrrr for the
next track to _I_S_R_C__n_u_m_b_e_r.
iiiinnnnddddeeeexxxx====_l_i_s_t
Sets an index list for the next track. In index list
is a comma separated list of numbers that are counting
from index 1. The first entry in this list must contain
a 0, the following numbers must be an ascending list of
numbers (counting in 1/75 seconds) that represent the
start of the indices. An index list in the form:
0,7500,15000 sets index 1 to the start of the track,
index 2 100 seconds from the start of the track and
Joerg Schilling Last change: Version 1.8.1 8
CDRECORD(1) Schily's USER COMMANDS CDRECORD(1)
index 3 200 seconds from the start of the track.
----aaaauuuuddddiiiioooo
If this flag is present, all subsequent tracks are
written in CCCCDDDD----DDDDAAAA (similar to Red Book) audio format.
The file with data for this tracks should contain
stereo, 16-bit digital audio with 44100 samples/s. The
byte order should be the following: MSB left, LSB left,
MSB right, LSB right, MSB left and so on. The track
should be a multiple of 2352 bytes. It is not possible
to put the master image of an audio track on a raw disk
because data will be read in multiple of 2352 bytes
during the recording process.
If a filename ends in ._a_u or ._w_a_v the file is con-
sidered to be a structured audio data file. CCCCddddrrrreeeeccccoooorrrrdddd
assumes that the file in this case is a Sun audio file
or a Microsoft .WAV file and extracts the audio data
from the files by skipping over the non-audio header
information. In all other cases, cdrecord will only
work correctly if the audio data stream does not have
any header. Because many structured audio files do not
have an integral number of blocks (1/75th second) in
length, it is often necessary to specify the ----ppppaaaadddd
option as well. ccccddddrrrreeeeccccoooorrrrdddd recognizes that audio data in
a .WAV file is stored in Intel (little-endian) byte
order, and will automatically byte-swap the data if the
CD recorder requires big-endian data. CCCCddddrrrreeeeccccoooorrrrdddd will
reject any audio file that does not match the Red Book
requirements of 16-bit stereo samples in PCM coding at
44100 samples/second.
Using other structured audio data formats as input to
ccccddddrrrreeeeccccoooorrrrdddd will usually work if the structure of the data
is the structure described above (raw pcm data in big-
endian byte order). However, if the data format
includes a header, you will hear a click at the start
of a track.
If neither -_d_a_t_a nor - _a_u_d_i_o have been specified,
ccccddddrrrreeeeccccoooorrrrdddd defaults to -_a_u_d_i_o for all filenames that end
in ._a_u or ._w_a_v and to -_d_a_t_a for all other files.
----sssswwwwaaaabbbb
If this flag is present, audio data is assumed to be in
byte-swapped (little-endian) order. Some types of CD-
Writers e.g. Yamaha, Sony and the new SCSI-3/mmc drives
require audio data to be presented in little-endian
order, while other writers require audio data to be
presented in the big-endian (network) byte order nor-
mally used by the SCSI protocol. CCCCddddrrrreeeeccccoooorrrrdddd knows if a
CD-Recorder needs audio data in big- or little-endian
Joerg Schilling Last change: Version 1.8.1 9
CDRECORD(1) Schily's USER COMMANDS CDRECORD(1)
order, and corrects the byte order of the data stream
to match the needs of the recorder. You only need the
-_s_w_a_b flag if your data stream is in Intel (little-
endian) byte order.
Note that the verbose output of ccccddddrrrreeeeccccoooorrrrdddd will show you
if swapping is necessary to make the byte order of the
input data fit the required byte order of the recorder.
CCCCddddrrrreeeeccccoooorrrrdddd will not show you if the -_s_w_a_b flag was actu-
ally present for a track.
----ddddaaaattttaaaa
If this flag is present, all subsequent tracks are
written in CCCCDDDD----RRRROOOOMMMM mmmmooooddddeeee 1111 (Yellow Book) format. The data
is a multiple of 2048 bytes. The file with track data
should contain an IIIISSSSOOOO----9999666666660000 or RRRRoooocccckkkk RRRRiiiiddddggggeeee filesystem
image (see mmmmkkkkiiiissssooooffffssss for more details). If the track data
is an uuuuffffssss filesystem image, fragment size should be set
to 2 KB or more to allow CR-drives with 2 KB sector
size to to be used for reading.
-data is the default, if no other flag is present.
If neither -_d_a_t_a nor - _a_u_d_i_o have been specified,
ccccddddrrrreeeeccccoooorrrrdddd defaults to -_a_u_d_i_o for all filenames that end
in ._a_u or ._w_a_v and to -_d_a_t_a for all other files.
----mmmmooooddddeeee2222
If this flag is present, all subsequent tracks are
written in CCCCDDDD----RRRROOOOMMMM mmmmooooddddeeee 2222 format. The data is a multiple
of 2048 bytes.
----xxxxaaaa1111 If this flag is present, all subsequent tracks are
written in CCCCDDDD----RRRROOOOMMMM XXXXAAAA mmmmooooddddeeee 1111 format. The data is a mul-
tiple of 2048 bytes.
----xxxxaaaa2222 If this flag is present, all subsequent tracks are
written in CCCCDDDD----RRRROOOOMMMM XXXXAAAA mmmmooooddddeeee 2222 format. The data is a mul-
tiple of 2048 bytes.
----ccccddddiiii If this flag is present, all subsequent tracks are
written in CCCCDDDDIIII format. The data is a multiple of 2048
bytes.
----iiiissssoooossssiiiizzzzeeee
Use the IIIISSSSOOOO----9999666666660000 file system size as the size of the
next track. This option is needed if you want to read
the image of a track from a raw disk partition or on a
master CD. In the first case the option ----iiiissssoooossssiiiizzzzeeee is
needed to limit the size of the CD to the size of the
ISO filesystem. In the second case the option ----iiiissssoooossssiiiizzzzeeee
is needed to prevent ccccddddrrrreeeeccccoooorrrrdddd from reading the two run
Joerg Schilling Last change: Version 1.8.1 10
CDRECORD(1) Schily's USER COMMANDS CDRECORD(1)
out blocks that are appended by each CD-recorder in
track at once mode. These two run out blocks cannot be
read and would cause a buffer under run that would
cause a defective copy. Do not use this option if
ccccddddrrrreeeeccccoooorrrrdddd reads the track data from _s_t_d_i_n. This option
currently cannot be used to determine the size of a
file system if the multi session option is present.
----ppppaaaadddd If the track is a data track, 15 sectors of zeroed
data will be added to the end of this and each subse-
quent data track. In this case, the ---- ppppaaaadddd option is
superseded by the ppppaaaaddddssssiiiizzzzeeee==== option. It will remain how-
ever as a shorthand for ppppaaaaddddssssiiiizzzzeeee====11115555ssss.... If the - _p_a_d
option refers to an audio track, ccccddddrrrreeeeccccoooorrrrdddd will pad the
audio data to be a multiple of 2352 bytes. The audio
data padding is done with binary zeroes which is equal
to absolute silence.
----ppppaaaadddd remains valid until disabled by ----nnnnooooppppaaaadddd.
ppppaaaaddddssssiiiizzzzeeee====#
Set the amount of data to be appended as padding to the
next track to #. Opposed to the behavior of the ----ppppaaaadddd
option, the value for _p_a_d_s_i_z_e= is reset to zero for
each new track. See ffffssss= option for possible arguments.
Use this option if your CD-drive is not able to read
the last sectors of a track or if you want to be able
to read the CD on a LLLLiiiinnnnuuuuxxxx system with the ISO-9660
filesystem read ahead bug. If an empty file is used
for track data, this option may be used to create a
disk that is entirely made of padding.
----nnnnooooppppaaaadddd
Do not pad the following tracks - the default.
pppprrrreeeeggggaaaapppp=#
Set the pre-gap size for the next track. This option
currently only makes sense with the TEAC drive when
creating track-at-once disks without the 2 second
silence before each track.
This option may go away in future.
----pppprrrreeeeeeeemmmmpppp
If this flag is present, all TOC entries for subsequent
audio tracks will indicate that the audio data has been
sampled with 50/15 ╡sec preemphasis. The data, however
is not modified during the process of transferring from
file to disk. This option has no effect on data tracks.
----nnnnoooopppprrrreeeeeeeemmmmpppp
If this flag is present, all TOC entries for subsequent
audio tracks will indicate that the audio data has been
Joerg Schilling Last change: Version 1.8.1 11
CDRECORD(1) Schily's USER COMMANDS CDRECORD(1)
mastered with linear data - this is the default.
ttttssssiiiizzzzeeee====####
If the master image for the next track has been stored
on a raw disk, use this option to specify the valid
amount of data on this disk. If the image of the next
track is stored in a regular file, the size of that
file is taken to determine the length of this track.
If the track contains an ISO 9660 filesystem image use
the -_i_s_o_s_i_z_e option to determine the length of that
filesystem image.
In Disk at Once mode and with some drives that use the
TEAC programming interface, even in Track at Once mode,
ccccddddrrrreeeeccccoooorrrrdddd needs to know the size of each track before
starting to write the disk. Cdrecord now checks this
and aborts before starting to write. If this happens
you will need to run mmmmkkkkiiiissssooooffffssss ----pppprrrriiiinnnntttt----ssssiiiizzzzeeee before and use
the output as an argument to the ttttssssiiiizzzzeeee= option of
ccccddddrrrreeeeccccoooorrrrdddd.
See ffffssss= option for possible arguments.
EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS
For all examples below, it will be assumed that the CD-
Recorder is connected to the primary SCSI bus of the
machine. The SCSI target id is set to 2.
To record a pure CD-ROM at double speed, using data from the
file _c_d_i_m_a_g_e._r_a_w:
cdrecord -v speed=2 dev=2,0 cdimage.raw
To create an image for a ISO 9660 filesystem with Rock Ridge
extensions:
mkisofs -R -o cdimage.raw /home/joerg/master/tree
To check the resulting file before writing to CD on Solaris:
mount -r -F fbk -o type=hsfs /dev/fbk0:cdimage.raw /mnt
On Linux:
mount cdimage.raw -r -t iso9660 -o loop /mnt
Go on with:
ls -lR /mnt
umount /mnt
If the overall speed of the system is sufficient and the
structure of the filesystem is not too complex, cdrecord
will run without creating an image of the ISO 9660
Joerg Schilling Last change: Version 1.8.1 12
CDRECORD(1) Schily's USER COMMANDS CDRECORD(1)
filesystem. Simply run the pipeline:
mkisofs -R /master/tree | cdrecord - v fs=6m speed=2
dev=2,0 -
The recommended minimum fifo size for running this pipeline
is 4 MBytes. As the default fifo size is 4 MB, the ffffssss====
option needs only be present if you want to use a different
fifo size. If your system is loaded, you should run mkisofs
in the real time class too. To raise the priority of
mmmmkkkkiiiissssooooffffssss replace the command
mkisofs -R /master/tree
by
priocntl -e -c RT -p 59 mkisofs -R /master/tree
on Solaris and by
nice --18 mkisofs -R /master/tree
on systems that don't have UUUUNNNNIIIIXXXX IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaallll compliant
realtime scheduling.
Cdrecord runs at priority 59 on Solaris, you should run
mkisofs at no more than priority 58. On other systems, you
should run mkisofs at no less than nice --18.
Creating a CD-ROM without file system image on disk has been
tested on a Sparcstation-2 with a Yamaha CDR-400. It did
work up to quad speed when the machine was not loaded. A
faster machine may be able to handle quad speed also in the
loaded case.
To record a pure CD-DA (audio) at single speed, with each
track contained in a file named _t_r_a_c_k_0_1._c_d_a_u_d_i_o,
_t_r_a_c_k_0_2._c_d_a_u_d_i_o, etc:
cdrecord -v speed=1 dev=2,0 -audio track*.cdaudio
To check if it will be ok to use double speed for the exam-
jjjjooooeeeerrrrgggg@@@@sssscccchhhhiiiillllyyyy....iiiissssddddnnnn....ccccssss....ttttuuuu----bbbbeeeerrrrlllliiiinnnn....ddddeeee or jjjjssss@@@@ccccssss....ttttuuuu----bbbbeeeerrrrlllliiiinnnn....ddddeeee or
